|
•
|
Automated: Once executed, the WEM installation file detects previously installed versions of the application. If an older version is present, you are prompted as to whether or not you would like to perform an upgrade.
|
|
•
|
Manual: This type involves uninstalling any existing instances of the application and installing the new version.
|
This type must be used if the current instance is more than two releases older than the new version being installed. For example, the manual upgrade type must be used if 3.5.x is currently installed and you would like to upgrade to 5.1.x.
Caution: Please contact your local support representative to ensure compatibility prior to upgrading.
Important: The WEM application does not provide an automated mechanism for performing software “downgrades” (reverting to an older software version from a newer one). However, the instructions provided in the Performing a Manual Upgrade section of this chapter can be used since that procedure requires you to uninstall the existing version and install the alternate. Information is also provided for migrating database information.
Important: Unless otherwise specified, all information in this chapter applies to both Sun Solaris- and Red Hat Enterprise Linux-based WEM systems.
Important: Make sure that you check the status of your system with your system administrator. The information in the “Pre-Upgrade Checklist” will need to be verified and recorded before proceeding to the section Performing an Automated Upgrade or Performing a Manual Upgrade .You can enable/disable XML report generation of the bulk statistics by using “Generate XML Files”. Alternatively, it can be enabled/disabled by configuring the XMLDataEnable parameter to 1 in the bsserver.cfg file (in the /<ems_dir>/server/etc directory by default). If enabled, the files are stored on the EMS server (the /<ems_dir>/server/xmldata directory by default).
file_name is the name of the WEM application installation file.
|
•
|
setup.bin: The installation binary file.
|
|
•
|
inst: The executable file used to initiate the installation. This file is used for both the console- and the GUI-based methods.
|
|
•
|
uninst: Once the WEM application has been installed, this file must be copied to the /<ems_dir>/_uninst/ directory. It is the executable file for uninstalling the application for both the console- and GUI-based methods.
|
|
•
|
file_name.tar: A compressed file containing all of the application files required for both the script- and GUI-based installation methods.
|
|
•
|
README: A text file containing information pertaining to the release.
|
|
Step 4
|
Proceed to either the Performing an Automated Upgrade or Performing a Manual Upgrade section of this chapter.
|
|
•
|
GUI-based method: This method is the most often used installation procedure. Requirements for using this method include:
|
|
•
|
Console-based method: This method is available to users who do not have an X-Windows client available for remote network connectivity to the WEM server via Telnet or SSH.
|
Depending on the desired installation method, proceed to either the Upgrading the WEM Software using the Console-Based Installation Method or Upgrading the WEM Software using the GUI-Based Installation Wizard section of this chapter.
|
Step 3
|
Click the Next button. The system automatically checks for an installed version of the application. If a version is installed, a warning dialog appears.
|
|
Step 4
|
Click Yes to proceed.
|
|
Step 5
|
Follow the on-screen prompts to progress through the various installation dialogs and configure the parameters as required. Refer to the WEM Installation Parameter Descriptions table for descriptions of the configurable parameters on each of the installation dialogs.
|
|
Step 6
|
Click the Finish button to exit the GUI-based installation wizard.
|
Important: The NorthBound Server and Notification Service processes are customer-specific and are not operational without the appropriate license. Please contact your local sales representative for additional information.All log files are stored in the /<ems_dir>/server/log directory by default. Refer to the log files for additional information in the event that one or more of the processes did not start properly.
|
Step 8
|
Copy the uninstallation script to the _uninst directory created during the installation process (/<ems_dir>/_uninst by default) by entering the following command:
|
|
Step 9
|
Copy the files pertaining to the migrate script to the scripts directory created during the installation process (/<ems_dir>/server/scripts by default) by entering the following command:
|
|
Step 3
|
Enter “1” to proceed to the EMS Upgrade Check configuration prompts. The system automatically checks for installed version of the application. If a version is installed, a message appears asking if you would like to upgrade the current installation.
|
|
Step 4
|
|
Step 5
|
Follow the on-screen prompts to proceed through the upgrade and configure the various parameters as required. Refer to the WEM Installation Parameter Descriptions table for descriptions of the configurable parameters within each of the sections of the script.
|
Important: The NorthBound Server and Notification Service processes are customer-specific and are not operational without the appropriate license. Please contact your local sales representative for additional information.All log files are stored in the /<ems_dir>/server/log directory by default. Refer to log files for additional information in the event that one or more of the processes did not start properly.
|
Step 8
|
Copy the un-installation script to the _uninst directory created during the installation process (/<ems_dir>/_uninst by default) by entering the following command:
|
|
Step 9
|
Copy the files pertaining to the migrate script to the scripts directory created during the installation process (/<ems_dir>/server/scripts by default) by entering the following command:
|
Important: The instructions in this section can also be used to perform a software downgrade of the WEM if required.|
Step 1
|
|
Step 2
|
Optional. If you wish to preserve database information for the currently installed version, follow the instructions in the Performing a Database Back-Up using the backup Script section of this chapter and then proceed to Step 3 of this procedure.
|
|
Step 3
|
Uninstall the WEM using the instructions provided in the Uninstalling The WEM chapter of this guide and proceed to Step 4 of this procedure.
|
|
Step 4
|
Install the desired version of the WEM using the instructions provided in the Installing the WEM Software chapter of this guide and proceed to Step 5 of this procedure.
|
|
Step 5
|
Optional. If database information was backed-up per Step 2 of this procedure, restore the data using the instructions in the Performing a Database Restoration using the backup Script section of this chapter and proceed to Step 6 of this procedure.
|
|
Step 6
|
Start WEM Server processes using the instructions in the Step 3: Start WEM Server Application section of WEM Server Files and Operation chapter of this guide.
|
|
Step 2
|
In the main menu, go to Accounting > Bulk Statistics Configuration. The Bulk Statistics dialog box opens.
|
|
Step 3
|
Click the Configure button to launch the Bulk Statistics Configuration dialog box.
|
|
Step 4
|
|
Step 5
|
After selecting all the configured schemas, click the Delete icon. Warning message displays.
|
|
Step 6
|
Click Yes to delete the selected schemas and click the Apply button. Another warning message displays.
|
|
Step 7
|
Click No to ignore the warning. The successful configuration message displays.
|
|
Step 8
|
Click OK to finish.
|
|
Step 2
|
In the main menu, go to Accounting > Bulk Statistics Configuration. The Bulk Statistics dialog box opens.
|
|
Step 3
|
Click the Configure button to launch the Bulk Statistics Configuration dialog box.
|
|
Step 4
|
|
Step 5
|
Click the Apply button to configure the selected schemas. You may get a warning message “You have selected some obsolete and/or WEM unsupported counters. Unsupported counters will not be parsed by WEM. Do you want to continue?”
|
|
Step 6
|
Click Yes to close the warning. The successful configuration message displays.
|
|
Step 7
|
Click OK to finish configuring schemas.
|
Database preservation is done using the backup.sh script located in the /<ems_dir>/server/scripts directory by default. This script is used to perform both database back-ups and restorations.
Important: The instructions provided in this section are intended for use with those located in the Performing a Manual Upgrade section of this chapter.|
Step 1
|
This script automatically stops all WEM processes and takes the backup of the WEM database using pg_dumpall command. You are notified once the back-up is complete.
|
Step 3
|
Important: The instructions provided in this section are intended for use with those located in the Performing a Manual Upgrade section of this chapter.|
Step 1
|
|
Step 3
|
